Hand hygiene compliance system

ABSTRACT

A system and method for performing hand hygiene compliance. The method includes receiving a notification that an individual has entered a physical location. The notification is received by a node in a wireless mesh network that includes a plurality of nodes corresponding to objects in the physical location. A hand hygiene protocol is identified for the individual. It is determined that the individual has not followed the hand hygiene protocol. The determining is performed by software executing on the nodes in the wireless mesh network and responsive to a previous and a current location of the individual relative to the objects in the physical location. The individual is notified in response to determining that the individual has not followed the hand hygiene protocol.

CROSS-REFERENCE TO RELATED APPLICATIONS

The present application is a continuation of U.S. application Ser. No.13/114,216, filed May 24, 2014, which claims the benefit of provisionalapplication No. 61/347,715 filed May 24, 2010, the content of which arehereby incorporated by reference in their entireties herein.

BACKGROUND OF THE INVENTION

The subject matter disclosed herein relates generally to hand hygienecompliance (HHC), and particularly to tracking and encouraging workercompliance with hand hygiene protocols. In a hospital setting, hospitalassociated infections (HAIs) may cause undue illness to patients. Oneway of decreasing the number of HAIs is for hospital workers to washtheir hands at key phases of patient care. In an effort to reduce thenumber of HAIs, hospitals have implemented hand hygiene protocols forhospital staff. For example, staff at a hospital may be instructed towash their hands when they enter a patient room, before any patientcontact, before an aseptic task, after body fluid exposure risk, afterpatient contact, after contact with patient surroundings, and uponexiting the patient room.

Hospitals have a variety of techniques for reminding workers to followhand hygiene protocols and for tracking worker compliance with handhygiene protocols. One method of reminding workers to follow handhygiene protocols is to send a signal (e.g., an audio or visualreminder) to the health care worker (HCW) when the HCW enters or exits apatient's room. This method works well when hand hygiene requirementsare the same for all patients and when the requirements are associatedwith a HCW being at a particular location. This method does not workwell when hand hygiene requirements differ across patients, when therequirements differ based on a particular path taken by the HCW, and/orthey differ based on an amount of time spent by the HCW at a particularlocation (e.g., next to the patient's bed). One method of tracking handhygiene compliance (HHC) is to use “secret shoppers” to watch the staffto see if they are following the protocol. The secret shoppers mayremind the HCWs and/or they may report on compliance. One drawback tothe use of secret shoppers is that knowledge of the secret shoppers cancause an artificial spike in hand hygiene compliance, because theworkers know that they are being watched.

Accordingly, and while existing HHC systems may be suitable for theirintended purpose, there remains a need in the art for HHC systems thatovercome these drawbacks.

This background information is provided to reveal information believedby the applicant to be of possible relevance to the present invention.No admission is necessarily intended, nor should be construed, that anyof the preceding information constitutes prior art against the presentinvention.

BRIEF DESCRIPTION OF THE INVENTION

An embodiment of the invention is a computer implemented method forperforming hand hygiene compliance (HHC). The method includes receivinga notification that an individual has entered a physical location. Thenotification is received by a node in a wireless mesh network thatincludes a plurality of nodes corresponding to objects in the physicallocation. A hand hygiene protocol is identified for the individual. Itis determined that the individual has not followed the hand hygieneprotocol. The determining is performed by software executing on thenodes in the wireless mesh network and is responsive to a previous and acurrent location of the individual relative to the objects in thephysical location. The individual is notified in response to determiningthat the individual has not followed the hand hygiene protocol.

An embodiment of the invention is a HHC system. The system includes aplurality of nodes corresponding to objects in a physical location,where the nodes form a wireless mesh network. The system also includesHHC software for execution on the nodes in the wireless mesh network toperform a method. The method includes receiving a notification that anindividual has entered the physical location and identifying a handhygiene protocol for the individual. The method also includesdetermining that the individual has not followed the hand hygieneprotocol. The determining is responsive to a previous and a currentlocation of the individual relative to the objects in the physicallocation. The method further includes notifying the individual inresponse to determining that the individual has not followed the handhygiene protocol.

Another embodiment of the invention is a computer program product forperforming HHC. The computer program product includes a tangible storagemedium readable by a processing circuit and storing instructions forexecution by the processing circuit for performing a method. The methodincludes receiving a notification that an individual has entered aphysical location. The notification is received by a node in a wirelessmesh network that includes a plurality of nodes corresponding to objectsin the physical location. A hand hygiene protocol is identified for theindividual. It is determined that the individual has not followed thehand hygiene protocol. The determining is performed by softwareexecuting on the nodes in the wireless mesh network and is responsive toa previous and a current location of the individual relative to theobjects in the physical location. The individual is notified in responseto determining that the individual has not followed the hand hygieneprotocol.

A further embodiment of the invention is a computer implemented methodfor performing HHC. The method includes receiving a notification that anindividual has entered a first physical location. The notification isreceived by a node in a wireless mesh network that includes a pluralityof nodes corresponding to objects in the first physical location. A handhygiene protocol is identified for the individual. It is determined thatthe individual has not followed the hand hygiene protocol. Thedetermining is performed by software executing on a processor located ina second physical location, the determining responsive to a previous anda current location of the individual relative to the objects in thefirst physical location. The individual is notified in response todetermining that the individual has not followed the hand hygieneprotocol.

A further embodiment of the invention is a system for performing HHC.The system includes a plurality of nodes corresponding to objects in afirst physical location. The plurality of nodes form a wireless meshnetwork. The system also includes HHC software for execution on aprocessor located in a second physical location for performing a method.The second physical location is different than the first physicallocation. The method includes receiving a notification that anindividual has entered the first physical location and identifying ahand hygiene protocol for the individual. The method also includesdetermining that the individual has not followed the hand hygieneprotocol. The determining is responsive to a previous and a currentlocation of the individual relative to the objects in the first physicallocation. The method further includes notifying the individual inresponse to determining that the individual has not followed the handhygiene protocol.

A further embodiment of the invention is a computer program product forperforming HHC. The computer program product includes a tangible storagemedium readable by a processing circuit and storing instructions forexecution by the processing circuit for performing a method. The methodincludes receiving a notification that an individual has entered a firstphysical location. The notification is received by a node in a wirelessmesh network that includes a plurality of nodes corresponding to objectsin the first physical location. A hand hygiene protocol is identifiedfor the individual. It is determined that the individual has notfollowed the hand hygiene protocol. The determining is performed bysoftware executing on a processor located in a second physical location,the determining responsive to a previous and a current location of theindividual relative to the objects in the first physical location. Theindividual is notified in response to determining that the individualhas not followed the hand hygiene protocol.

BRIEF DESCRIPTION OF THE DRAWINGS

Referring to the exemplary drawings wherein like elements are numberedalike in the accompanying Figures:

FIG. 1 depicts a hand hygiene compliance (HHC) system that may beimplemented in accordance with an embodiment;

FIG. 2 depicts application, instruction, and transport layers that maybe implemented in accordance with an embodiment;

FIG. 3 depicts a HHC system that spans two physical locations that maybe implemented in accordance with an embodiment;

FIG. 4 depicts a mesh network spanning a hospital that may beimplemented in accordance with an embodiment;

FIG. 5 depicts a mesh network spanning a section of a hospital that maybe implemented in accordance with an embodiment;

FIG. 6 depicts a subset of a mesh network spanning a room that may beimplemented in accordance with an embodiment;

FIG. 7A depicts an example process flow that may be implemented when aHCW enters a patient's room and FIG. 7B depicts a portion of a meshnetwork that may participate in the process flow depicted in FIG. 7A, inaccordance with an embodiment;

FIG. 8 depicts HCW reminders that may be generated in accordance with anembodiment;

FIG. 9 depicts a process flow that may be implemented when a HCWinteracts with a patient in accordance with an embodiment;

FIG. 10 depicts a process flow that may be implemented in a restroom inaccordance with an embodiment;

FIG. 11 depicts a process flow for monitoring HHC and changing HCWpreferences in accordance with an embodiment;

FIG. 12 depicts a system for providing mobile monitoring in accordancewith an embodiment;

FIGS. 13A and 13B depict systems for bridging the HHC system to anexisting network in accordance with various embodiments; and

FIG. 14 depicts a badge that may be implemented in accordance with anembodiment.

DETAILED DESCRIPTION OF THE INVENTION

Although the following detailed description contains many specifics forthe purposes of illustration, anyone of ordinary skill in the art willappreciate that many variations and alterations to the following detailsare within the scope of the invention. Accordingly, the followingembodiments of the invention are set forth without any loss ofgenerality to, and without imposing limitations upon, the claimedinvention.

An embodiment of the invention, as shown and described by the variousfigures and accompanying text provides a hand hygiene compliance (HHC)system. An embodiment of the system monitors healthcare worker (HCW)compliance with a hand hygiene protocol. If a HCW is not following theprotocol, reminders are sent to the HCW. In addition, the non-compliancemay be reported to a supervisor or other HHC personnel. An embodimentprovides for two-way communication between an integrated circuit (IC)located on an employee badge and ICs corresponding to various objects(e.g., located on or integrated into) in a hospital. In an embodiment,the ICs on the badge and other objects are nodes in a wireless meshnetwork and include application software, mesh network protocols, andstorage locations. The two-way communication between the nodes allowsfor more granular tracking of HCW actions that may require hand hygiene,for more reminders to the HCWs, and for more targeted reminders to theHCWs. In addition, the ability to store data at a node can provide formore customized hand hygiene instructions. For example, a node at apatient bed may store information about the status of the patient (e.g.,staph infection). The node at the patient bed can communicate with anode in a sink and a node in a badge that the HCW is wearing to assurethat the HCW has followed the procedure associated with the patientstatus (e.g., wash hands for three minutes and use soap with higherantibacterial content).

In an embodiment, a specific application is implemented on each node.This specific application, implemented by an application layer, is usedto interface with the object and with nodes on other objects to assurethat a specific process of HHC has been completed (e.g., that a handhygiene protocol has been followed by a HCW). An example is that a nodeon a soap dispenser will relay location information but also can tellwhether or not a HCW used soap from the soap dispenser. In addition, asink node may relay location information and can also monitor theduration of hand scrubbing. In addition, the application layer maycommunicate to nodes on the soap dispenser and the sink to assure thatboth processes were performed by the same HCW, in order to assure thatproper hand hygiene was performed. Examples of objects associated withnodes having application layers include, but are not limited to: beds,sanitizing gel dispensers, badges, room sensors, and any other objectthat is either involved in hand hygiene or contamination areas.

An example system implemented by an embodiment includes a badge nodelocated on a HCW, an object node located at a door to a patient room, anobject node located on a patient bed, and an object node located on asoap dispenser. One scenario for using the system includes the HCWentering the patient room. The object node located on the patient bedcommunicates the patient care requirements (e.g., hand hygienerequirements) to the other nodes in the network. If the HCW enters theroom and walks towards the patient bed without exercising proper handhygiene, the soap dispenser will communicate to the node on the badgeand to the node on the bed that the soap dispenser has not been used.Then, the nodes (badge, soap dispenser, and bed) can use their relativeproximity to determine that hand hygiene actions that should have beenperformed by the HCW have not been performed. In response to thisdetermination, the HCW's badge flashes (or takes some action to get theHCW's attention and/or a supervisor's attention, such as vibrate forexample) and/or the soap dispenser beeps (or takes some action to getthe HCW's attention). Alternatively, if the HCW enters the room andperforms hand hygiene, then the object node located on the soapdispenser may verify that the patient care requirements have been met(type of soap, length of washing, hand drying, etc.). All or a subset ofthe actions detected, as well as any other activities associated withthe hand hygiene protocol, may be logged and reported.

FIG. 1 depicts a HHC system implemented in accordance with anembodiment. The system depicted in FIG. 1 includes a wireless meshnetwork 114 made up of one or more badge nodes 102 and object nodes 104.As depicted in FIG. 1, the wireless mesh network 114 is in communication(e.g., via a transmission control protocol/Internet protocol or “TCP/IP”connection) with an existing network 106 for accessing a hostapplication located on a host system 110. In an embodiment, the existingnetwork 106 (e.g., an existing IT network) is implemented by a localarea network (LAN). It will be appreciated that existing network 106 canbe implemented using other types of networks such as, but not limited tothe Internet, and an intranet. As depicted in FIG. 1, existing network106 is in communication with the host system 110, a storage device 112,and a user device 108. The wireless mesh network 114 depicted in FIG. 1covers one room. It will be appreciated that the system includes aplurality of wireless mesh networks 114. Each wireless mesh network 114may span a variety of physical locations (also referred to herein asphysical areas) such as, but not limited to, a single room, a group ofrooms, a floor, a building, and two or more buildings. In an embodiment,the host system 110 is implemented by one or more processors, each ofwhich may be located in the same physical location or a differentphysical location than the wireless mesh network.

Advantages to utilizing a wireless mesh network 114 includes the abilityto provide seamless integration into existing buildings, independentoperation from existing networks, self healing network if a node isdamaged, sub-room level real-time asset tracking, ease of installationand maintenance, and ease of expandability.

Badge node 102 is located on a badge worn by a HCW. The badge node 102includes network protocols, storage locations, and application software.The network protocols are used to transmit packets from the badge node102 to the object nodes 104 (and to other badge nodes 102 if present innetwork 114) in wireless mesh network 114. The badge storage storesinformation associated with the HCW such as, but not limited to: name,occupation, specific hand hygiene procedures, location history includingdifferent contamination level zones, HHC history and accuracy,notification preferences. In an embodiment, the storage locations areimplemented by a storage mechanism such as, but not limited to, randomaccess memory (RAM) or nonvolatile memory (NVM).

In an embodiment, the application software located on the badge node 102implements the functions described herein to perform HHC including:locating the HCW, determining a possible HHC protocol violation,reminding the HCW of the hand hygiene protocol, and reporting thepossible violation. It will be appreciated that the badge node 102 maybe located on the HCW by means other than a badge. For example, thebadge node 102 may be located on a belt worn by the HCW or attached to aportable hand sanitizer carried by the HCW.

In an embodiment, locating the HCW is performed by a real time locationsystem (RTLS) 103 using a methodology such as active radio frequencyidentification, infrared hybrid, optical locating, low-frequencysignpost identification, semi-active radio frequency identification,ultrasound identification, ultrasonic ranging, ultrawide band,wide-over-narrow band, wireless local area network, and radio frequencytransceivers. These methodologies may use a variety of algorithms todetermine locations (e.g., of the HCWs) including, but not limited to:angle of arrival, line-of-sight, time of arrival, time difference ofarrival, received channel power indicator, received signal strengthindication, time of flight, symmetrical double sided—two way ranging,and near-field electromagnetic ranging. The RTLS 103 may be implementedvia application software located on the badge node 102 and/or one ormore object nodes 104.

In an embodiment, object nodes 104 are located on objects in a building.In the example depicted in FIG. 1, object nodes 104 are located on apatient bed, a soap dispenser, and at a sink. An object node 104includes network protocols, storage locations, and application software.The network protocols are used to transmit and receive packets, and theapplication software implements functions described herein. The storagelocations store information associated with the object such as, but notlimited to: patient instructions, specific hand hygiene procedures,contamination zone level, HHC history and accuracy, notificationpreferences.

In an embodiment, an object node 104 is integrated into an object suchas a soap dispenser or towel dispenser. In an embodiment, the objectnode 104 is built into the object during manufacturing and the HHCfunctionality described herein is enabled by providing a software key(or any other manner).

The user device 108 depicted in FIG. 1 is utilized to access the hostapplication executing on host system 110. In an embodiment, the hostapplication includes software instructions to set application parameterson the badge nodes 102 and object nodes 104, to generate reports on HHC,to provide software updates to the badge nodes 102 and object nodes 104,to store reports in the storage device 112, and to performadministrative functions (e.g., set up access security, and add users).In an embodiment, the host application includes software instructions tolocate the HCW, to determine a possible HHC protocol violation, toremind the HCW of the hand hygiene protocol, and to report the possibleviolation.

In an embodiment, the user device 108 is used to monitor current HHCdata related to a selected portion of a hospital (e.g., a room, a floor,a department). In an embodiment, access to monitor HHC data isrestricted and only authorized users are given access to selectedportions of the HHC data. For example, one user may be able to accessHHC data for only one room, while another user may be given access toHHC data for a group of rooms or for an entire floor. In an embodiment,current HHC data is stored in storage device 112 and status is monitoredvia the user device 108. In another embodiment, all or a portion of theHHC data is not reported back to the host application.

In an embodiment, the host application is executed by an object node 104located in wireless mesh network 114. The host application executing onan object node 104 may include a subset of the functionality providedwhen the host application executes on the host computer 110. In anembodiment, the subset includes monitoring and no reporting. In thismanner, no reporting is sent back to a central location and the systemis used to increase compliance, as opposed to also being used to reportnon-compliance.

FIG. 2 depicts application, instruction, and transport layersimplemented in accordance with an embodiment. The application layer 202depicted in FIG. 2 includes the application software and storagelocations to carry out the node functions described herein. Theapplication software is customized based on customer hand hygieneprotocols. In an embodiment, all of the nodes (including the badge nodes102 and the object nodes 104) contain the same software. In thisembodiment, the object nodes 104 and badge nodes 102 may includecustomizations to differentiate them from each other, with thecustomizations stored in storage locations on the object nodes 104 andbadge nodes 102. In another embodiment, the badge nodes 102 contain oneset of software instructions and the object nodes 104 contain adifferent set of software instructions. In a further embodiment, two ofmore of the object nodes 104 contain a different set of softwareinstructions tailored to the attached object.

Also depicted in FIG. 2, is an instruction layer 204, transport layer206, and communication conduit 208 to carry out the networking functionsdescribed herein. In an embodiment, the instruction layer 204 andtransport layer 206 are implemented using off the shelf software, andthe communication conduit 208 is implemented using off the shelfhardware. In the embodiment depicted in FIG. 2, the instruction layer204 is a native mesh implemented by using the standard command classstructure of the selected protocol. These types of command classes mayor may not have existing classes for HHC objects (i.e., a soap dispenserdevice command class). In many cases there will be no class structurefor objects in the HHC system and a more generic command class will beused (e.g., for the soap dispenser, a single pull light switch deviceclass, which will be on or off may be used). Another example is that acommand class for a dimmer may be used to generate a percentage of runtime on a pump in an alcohol dispenser to aid in determining how much ofthe alcohol was dispensed to a HCW.

In the embodiment depicted in FIG. 2, the transport layer 206 is a meshprotocol that interacts with the application layer 202 to communicatespecific information pertaining to the HHC system. The application layer202 handles the new HHC classes of devices and translates them intostandard instruction layer device classes so that these new deviceclasses can communicate directly with the mesh protocol in the transportlayer 206. As shown in FIG. 2, the transport layer 206 is implemented bya wireless mesh network communication protocol, such as, but not limitedto: ANT, ZigBee, and ZWave. In the embodiment depicted in FIG. 2, thetransport layer 206 allows for new objects and commands to be enteredinto the network and decisions about them being handled by the deviceitself, or some variant of many other devices.

It will be appreciated that one reason that the ANT protocol may bepreferable over the ZigBee protocol is because of battery life. Atransport layer 206 implemented in the ANT protocol consumes much lessbattery power than a transport layer 206 implemented n ZigBee. Devicesusing the ZigBee protocol are usually utilized for line power, andtherefore, built for use in the lighting industry. In the ZigBeeprotocol the battery powered nodes are in a separate network than theline powered nodes. This is done to save battery life, because a batterypowered node does not have to awake all of the time to be ready to passmessages in a ZigBee implementation. In the HHC system, the badge nodeand object nodes need to be awake at all times and ready to passmessages.

In the embodiment depicted in FIG. 2, the communication conduit 208 is aradio frequency (RF) transceiver operating at between 900 megahertz(MHZ) and 2.4 gigahertz (GHZ) to provide a wireless connection for thenodes. However, other frequencies are contemplated. The instructionlayer 204 communicates with the communication conduit 208 to providewireless communication between the object nodes 104 and badge nodes 102.

A mesh network can be broken up into small subparts, referred to hereinas “meshlets.” When another node that can communicate with the nodes ina meshlet (e.g., it “speaks” the same language as the meshlet), comesinto proximity of the meshlet, the other node and the nodes in themeshlet can all start communication. In an embodiment, the ability forthe badge node 102 to communicate to object nodes 104 (and any otherbadge nodes 102) in the meshlet is used to determine if a HCW is in aroom, how close the HCW is to a patient bed, and other data.

FIG. 3 depicts an embodiment of a HHC system that spans two physicallocations. As depicted in FIG. 3, a HHC system in a clinic 302 is incommunication with an HHC system in a hospital via, for example, anexisting TCIP infrastructure. The ability to link HHC systems togetherallows user devices with monitoring dashboards associated with the HHCsystems to be located in any facility. Thus, the hospital 304 canmonitor HHC at the clinic 302.

FIG. 4 depicts a parent mesh network spanning a hospital that isimplemented in accordance with an embodiment. As depicted in FIG. 4, thephysical location covered by the parent mesh network is the entirehospital 402. The parent mesh network depicted in FIG. 4 is made up of aplurality of meshlets.

FIG. 5 (with periodic reference back to elements shown in FIG. 4)depicts a parent meshlet that spans a section 502 of the hospital 402that is implemented in accordance with an embodiment. As depicted inFIG. 5, the physical location covered by the parent meshlet is a section502 of the hospital 402 such as a floor, a group, a wing, and/or adepartment. The parent meshlet depicted in FIG. 5 is made up of aplurality of micro meshlets and may also contain additionaltransceivers. In an embodiment, a meshlet (parent, micro, etc.) can bethought of as a team of nodes that are designed to perform a task, andthat task is HHC for a room or a floor. The team of nodes in the meshletcommunicate to each other at much higher frequencies than to a node at adifferent part of the hospital (even though communication is possible).The meshlet, which may contain other meshlets, works to ensure HHC forthat room, or other defined space. In an embodiment, nodes located on asoap dispenser, a bed and a sink are in control of a room and don'trequire any outside information (e.g., information from nodes) tocomplete the task of ensuring HHC for the room. A plurality of theseroom meshlets may be combined to complete the task of ensuring HHC for afloor. In this case, all of the rooms on the floor work together toassure HHC on the floor so they have formed a meshlet.

FIG. 6 depicts a micro meshlet that is contained in a hospital room inaccordance with an embodiment. As depicted in FIG. 6, the physicallocation covered by the meshlet is the hospital room. The meshletincludes a badge node 102, a portable hand sanitizer 708, and aplurality of object nodes 104 located at a towel dispenser 11, a sinkmonitor 12, a bed monitor or dispenser 13, and several foam dispensers14.

FIGS. 7A and 7B depicts a process flow that is implemented by anembodiment of the HHC system when a HCW enters a patient's room inaccordance with an embodiment. At block 702, the HCW enters the room andis identified by the nearest object node 104, which in this example, islocated on an alcohol foam dispenser. The HCW is identified when a badgenode 102 located on the HWC initiates a communication with the objectnodes 104 in the room, the communication including information about theHCW such as employee identification. The object node 104 waits forcompliance with a hand hygiene protocol that includes applying alcoholfoam while the HCW is in short range. At block 704, if hand hygiene isperformed using the alcohol foam dispenser, then no reminder istriggered and the event is logged. In an embodiment, the event is loggedinto a storage device that is accessible by monitoring and/or reportingfunctions. At block 706, if the HCW proceeds closer to the patient bedor closer to other nodes (other than a sink), then a reminder is sent tothe HCW. The HCW in FIG. 7B is wearing a portable hand sanitizer 708.

FIG. 8 depicts HCW reminders that are generated by the HHC system inaccordance with an embodiment. In an embodiment, the reminders includenotifying the HCW using one or more of an audio 3, visual, and hapticalert 4. The reminder may be customized by individual HCW or based onpatient needs. For example, if the HCW has a vibrating buzzer tag (anexample of a haptic alert), the HCW can set this as their preference.Similarly, the HCW can set a preference for an audible beep or lightemitting diode (LED) lights. Additionally, if the patient room needs tobe quiet, or policy requires minimal noise, the volume can be set foreach patient or globally. In one embodiment, object nodes 104 installedin outlets are used to perform tasks that require more power such asverbal audio reminders. In another embodiment, a wearable sanitizerdispenser with battery power for hands free operation utilizes thebattery for vibration. In some embodiments, an object node 104 and/or abadge node 102 may communicate with a ceiling node 105. The ceiling node105 may be in communication with other nodes of the wireless meshnetwork 114, network 106, user device 108, and/or the like, as indicatedby the dot-dashed lines.

FIG. 9 depicts a process flow implemented by an embodiment of the HHCsystem when a HCW interacts with a patient in accordance with anembodiment. As depicted in FIG. 9, a patient identifier object node 104located on a patient's wrist and/or a bed object node 104 located on thepatient's bed is used to track patient interaction. This allows the HHCsystem to offer reminders based on time or patient treatment. Forexample, if the patient requires aseptic tasks or there is a greaterchance of bodily fluid contact, more reminders can be triggered.

FIG. 10 depicts a process flow that is implemented by the HHC system toprovide HHC in another industry, such as the food service in accordancewith an embodiment. As depicted in FIG. 10, after the worker passes anobject node 104 located on the soap dispenser, or is in close proximityto the object node 104 located on the soap dispenser, the soap dispenseror the worker's badge generate a reminder to the worker. If the workeruses the dispenser, the reminder is quiet and the worker actions arerecorded. If no soap dispensing occurs, then failure is reported. Asdepicted in FIG. 10, optional object nodes 104 are located on a faucetand sink bowl to track washing details such as duration and scrub style.

It will be appreciated that embodiments are not limited to health careenvironments, and that embodiments can be utilized in any environment(e.g., health care, food service, education, etc.) where individuals(e.g., workers such as HCWs, visitors, patrons, etc.) are required tofollow a process.

FIG. 11 depicts a process flow for monitoring HCWs and for changing HCWpreferences in accordance with an embodiment. A HCW, with the propersecurity access, can view group HHC or personal HHC performance data ona display 1104. In addition, HCWs can change their personal reminderpreferences via the display 1104. As shown in FIG. 11, the display 1104is a node in the wireless mesh network. Also as shown in FIG. 11, thedisplay 1104 is connected to existing network 106 via a network bridge1102 to transfer HHC compliance data to a centrally located storagedevice 112. As shown in FIG. 11, a manager may then access the hostapplication on the host device 110, via the user device 108 to manageand observe results from the HHC system. Reports may be generatedautomatically or manually.

FIG. 12 depicts a system for providing mobile monitoring in accordancewith an embodiment. In the embodiment depicted in FIG. 12, a manager isobserving results from the HHC system via an application on a mobiletelephone 1202 or other mobile device, possibly in communication with aserver for mobile monitoring. For example, a manager may observe from amobile phone app via wi-fi or 3G, etc.

FIGS. 13A and 13B depict example systems for bridging the HHC system toan existing network in accordance with an embodiment. The HHC system inthe top portion of FIG. 13 is connected to existing network 106 via aUSB device 1302. The HHC system in bottom portion of FIG. 13 isconnected to existing network 106 via an ANT to WiFi or Ethernet device1304.

FIG. 14 depicts a badge 1402 that may be implemented in accordance withan embodiment. In the embodiment depicted in FIG. 14, the badge 1402 isinserted into a badge shape 1404 that provides one or more of sight,sound and feel reminder options. FIG. 14 also depicts a charging station1406 for charging the badge shape 1404.

Technical effects and benefits include the ability to more closelymonitor the position of a HCW within a room and to send more customizedreminders based on hand hygiene compliance opportunities that aredetected by nodes in a wireless mesh network. In addition, zone basedneeds may be enforced for notifications (e.g., no audio alerts in aquiet zone). Another benefit is the ability to use the system forreminders only, thus providing an opportunity to increase compliancewithout the drawbacks of the “secret shopper” method describedpreviously. A further benefit is the ability to integrate the HHC systemwith a RTLS 103 to locate HCWs and objects.

As will be appreciated by one skilled in the art, aspects of the presentinvention may be embodied as a system, method, or computer programproduct. Accordingly, aspects of the present invention may take the formof an entirely hardware embodiment, an entirely software embodiment(including firmware, resident software, micro-code, etc.) or anembodiment combining software and hardware aspects that may allgenerally be referred to herein as a “circuit,” “module” or “system.”Furthermore, aspects of the present invention may take the form of acomputer program product embodied in one or more computer readablemedium(s) having computer readable program code embodied thereon.

Any combination of one or more computer readable medium(s) may beutilized. The computer readable medium may be a computer readable signalmedium or a computer readable storage medium. A computer readablestorage medium may be, for example, but not limited to, an electronic,magnetic, optical, electromagnetic, infrared, or semiconductor system,apparatus, or device, or any suitable combination of the foregoing. Morespecific examples (a non-exhaustive list) of the computer readablemedium would include the following: an electrical connection having oneor more wires, a portable computer diskette, a hard disk, a randomaccess memory (RAM), a read-only memory (ROM), an erasable programmableread-only memory (EPROM or Flash memory), an optical fiber, a portablecompact disc read-only memory (CD-ROM), an optical storage device, amagnetic storage device, or any suitable combination of the foregoing.In the context of this document, a computer readable storage medium maybe any tangible medium that may contain, or store a program for use byor in connection with an instruction execution system, apparatus, ordevice.

A computer readable signal medium may include a propagated data signalwith computer readable program code embodied therein, for example, inbaseband or as part of a carrier wave. Such a propagated signal may takeany of a variety of forms, including, but not limited to,electro-magnetic, optical, or any suitable combination thereof. Acomputer readable signal medium may be any computer readable medium thatis not a computer readable storage medium and that can communicate,propagate, or transport a program for use by or in connection with aninstruction execution system, apparatus, or device.

Program code embodied on a computer readable medium may be transmittedusing any appropriate medium, including but not limited to wireless,wireline, optical fiber cable, RF, etc., or any suitable combination ofthe foregoing.

Computer program code for carrying out operations for aspects of thepresent invention may be written in any combination of one or moreprogramming languages, including an object oriented programming languagesuch as Java, Smalltalk, C++ or the like and conventional proceduralprogramming languages, such as the “C” programming language or similarprogramming languages. The program code may execute entirely on theuser's computer, partly on the user's computer, as a stand-alonesoftware package, partly on the user's computer and partly on a remotecomputer or entirely on the remote computer or server. In the latterscenario, the remote computer may be connected to the user's computerthrough any type of network, including a local area network (LAN) or awide area network (WAN), or the connection may be made to an externalcomputer (for example, through the Internet using an Internet ServiceProvider).

Aspects of the present invention are described with reference toflowchart illustrations and/or block diagrams of methods, apparatus(systems) and computer program products according to embodiments of theinvention. It will be understood that each block of the flowchartillustrations and/or block diagrams, and combinations of blocks in theflowchart illustrations and/or block diagrams, may be implemented bycomputer program instructions.

These computer program instructions may be provided to a processor of ageneral purpose computer, special purpose computer, or otherprogrammable data processing apparatus to produce a machine, such thatthe instructions, which execute via the processor of the computer orother programmable data processing apparatus, create means forimplementing the functions/acts specified in the flowchart and/or blockdiagram block or blocks. These computer program instructions may also bestored in a computer readable medium that may direct a computer, otherprogrammable data processing apparatus, or other devices to function ina particular manner, such that the instructions stored in the computerreadable medium produce an article of manufacture including instructionswhich implement the function/act specified in the flowchart and/or blockdiagram block or blocks.

The computer program instructions may also be loaded onto a computer,other programmable data processing apparatus, or other devices to causea series of operational steps to be performed on the computer, otherprogrammable apparatus or other devices to produce a computerimplemented process such that the instructions which execute on thecomputer or other programmable apparatus provide processes forimplementing the functions/acts specified in the flowchart and/or blockdiagram block or blocks.

The flowchart and block diagrams in the Figures illustrate thearchitecture, functionality, and operation of possible implementationsof systems, methods, and computer program products according to variousembodiments of the present invention. In this regard, each block in theflowchart or block diagrams may represent a module, segment, or portionof code, which comprises one or more executable instructions forimplementing the specified logical function(s). It should also be notedthat, in some alternative implementations, the functions noted in theblock may occur out of the order noted in the figures. For example, twoblocks shown in succession may, in fact, be executed substantiallyconcurrently, or the blocks may sometimes be executed in the reverseorder, depending upon the functionality involved. It will also be notedthat each block of the block diagrams and/or flowchart illustration, andcombinations of blocks in the block diagrams and/or flowchartillustration, may be implemented by special purpose hardware-basedsystems that perform the specified functions or acts, or combinations ofspecial purpose hardware and computer instructions.

While the invention has been described with reference to exampleembodiments, it will be understood by those skilled in the art thatvarious changes may be made and equivalents may be substituted forelements thereof without departing from the scope of the invention. Inaddition, many modifications may be made to adapt a particular situationor material to the teachings of the invention without departing from theessential scope thereof. Therefore, it is intended that the inventionnot be limited to the particular embodiment disclosed as the best modecontemplated for carrying out this invention, but that the inventionwill include all embodiments falling within the scope of the appendedclaims. Moreover, the use of the terms first, second, etc. do not denoteany order or importance, but rather the terms first, second, etc. areused to distinguish one element from another. Furthermore, the use ofthe terms a, an, etc. do not denote a limitation of quantity, but ratherdenote the presence of at least one of the referenced item.

1. A computer implemented method for monitoring the performance of handhygiene compliance, the method comprising: identifying, via a node in awireless mesh network, that an individual has entered a physicallocation, the wireless mesh network comprising a plurality of nodescorresponding to objects in the physical location; identifying a handhygiene protocol for the individual; determining that the individual hasnot followed the hand hygiene protocol; and in response to determiningthat the individual has not followed the hand hygiene protocol,generating a notification indicative thereof and viewable by theindividual, wherein the notification is generated at least in part basedupon one or more predefined preferences, the one or more predefinedpreferences being associated with at least one of the individual or oneor more parameters dependent upon the physical location.
 2. The methodof claim 1 wherein the notification is further generated based at leastin part on a patient status.
 3. The method of claim 1, wherein thenotifying includes one or more of an audio, visual, and haptic alert. 4.The method of claim 3, wherein the selection of the one or more of theaudio, visual, and haptic alert is based at least in part on the one ormore predefined preferences.
 5. The method of claim 1, furthercomprising transmitting data to a central monitoring location inresponse to determining that the individual has not followed the handhygiene protocol.
 6. The method of claim 1, further comprisingtransmitting data to a central monitoring location in response todetecting activity associated with the hand hygiene protocol.
 7. Acomputer implemented method for monitoring the performance of handhygiene compliance, the method comprising: identifying, via a node in awireless mesh network, that an individual has entered a physicallocation, the wireless mesh network comprising a plurality of nodescorresponding to objects in the physical location; identifying a handhygiene protocol for the individual, wherein the identified hand hygieneprotocol is identified at least in part by one or more nodes in thewireless mesh network and in the vicinity of the individual and is basedat least in part on a patient treatment that could be provided by theindividual in the physical location; determining that the individual hasnot followed the hand hygiene protocol; and notifying the individual inresponse to determining that the individual has not followed the handhygiene protocol.
 8. The method of claim 7 wherein the notification isfurther generated based at least in part on at least one of a statusassociated with a patient or characteristics of the physical location.9. The method of claim 7, wherein the notifying includes one or more ofan audio, visual, and haptic alert.
 10. The method of claim 9, whereinthe selection of the one or more of the audio, visual, and haptic alertis based at least in part on at least one of a status associated with apatient or characteristics of the physical location.
 11. The method ofclaim 7, further comprising transmitting data to a central monitoringlocation in response to determining that the individual has not followedthe hand hygiene protocol.
 12. The method of claim 7, further comprisingtransmitting data to a central monitoring location in response todetecting activity associated with the hand hygiene protocol.
 13. Acomputer implemented method for monitoring the performance of handhygiene compliance, the method comprising: identifying, via a node in awireless mesh network, that an individual has entered a physicallocation, the wireless mesh network comprising a plurality of nodescorresponding to objects in the physical location; identifying a handhygiene protocol for the individual, wherein the identified hand hygieneprotocol is identified at least in part by one or more nodes in thewireless mesh network and in the vicinity of the individual and is basedat least in part on a status associated with a patient in the vicinityof the individual; determining that the individual has not followed thehand hygiene protocol; and notifying the individual in response todetermining that the individual has not followed the hand hygieneprotocol.
 14. The method of claim 13 wherein the notification is furthergenerated based at least in part on characteristics of the physicallocation.
 15. The method of claim 13, wherein the notifying includes oneor more of an audio, visual, and haptic alert.
 16. The method of claim15, wherein the selection of the one or more of the audio, visual, andhaptic alert is based at least in part on at least one of the statusassociated with the patient or characteristics of the physical location.17. The method of claim 13, further comprising transmitting data to acentral monitoring location in response to determining that theindividual has not followed the hand hygiene protocol.
 18. The method ofclaim 13, further comprising transmitting data to a central monitoringlocation in response to detecting activity associated with the handhygiene protocol.